FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource OperationDefinition/FHIR Server from package hl7.fhir.uv.sdc.r4b#3.0.0 (94 ms)

Package hl7.fhir.uv.sdc.r4b
Type OperationDefinition
Id Id
FHIR Version R4B
Source http://hl7.org/fhir/uv/sdc/http://hl7.org/fhir/uv/sdc/STU3/OperationDefinition-Questionnaire-process-response.html
Url http://hl7.org/fhir/uv/sdc/OperationDefinition/Questionnaire-process-response
Version 3.0.0
Status draft
Date 2017-03-19
Name SDCQuestionnaireProcessResponse
Title Questionnaire Process Response
Experimental False
Realm uv
Authority hl7
Description This operation allows a system to 'receive' a QuestionnaireResponse for a particular Questionnaire. It is intended to be used by systems that expect to receive completed questionnaires but which do not necessarily want to host a RESTful endpoint where those responses are subsequently queryable. The receiver may choose to perform validation of the received response or against local business rules. There no response beyond an HTTP 200 OK if the response is consumed successfully, though an OperationOutcome can optionally be returned identifying warnings. If there are validation or other issues, the operation will fail with details in an OperationOutcome. The specific action that occurs on receipt of a form will depend on both the type of form and the submitter. It could trigger admission to a clinical trial, the beginning of an product investigation, the consideration of a patient's eligibility for coverage, etc. Alternatively, the data may simply be consumed and aggregated with other information for analysis or other use.
Type true
Kind operation

Resources that use this resource

CapabilityStatement
sdc-form-receiver SDC Form Receiver
sdc-form-receiver SDC Form Receiver

Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

SDCQuestionnaireProcessResponse

OPERATION: SDCQuestionnaireProcessResponse

The official URL for this operation definition is:

http://hl7.org/fhir/uv/sdc/OperationDefinition/Questionnaire-process-response

This operation allows a system to 'receive' a QuestionnaireResponse for a particular Questionnaire. It is intended to be used by systems that expect to receive completed questionnaires but which do not necessarily want to host a RESTful endpoint where those responses are subsequently queryable. The receiver may choose to perform validation of the received response or against local business rules. There no response beyond an HTTP 200 OK if the response is consumed successfully, though an OperationOutcome can optionally be returned identifying warnings. If there are validation or other issues, the operation will fail with details in an OperationOutcome. The specific action that occurs on receipt of a form will depend on both the type of form and the submitter. It could trigger admission to a clinical trial, the beginning of an product investigation, the consideration of a patient's eligibility for coverage, etc. Alternatively, the data may simply be consumed and aggregated with other information for analysis or other use.

URL: [base]/Questionnaire/$process-response

URL: [base]/Questionnaire/[id]/$process-response

Input parameters Profile: Questionnaire process response operation input parameters

Parameters

UseNameCardinalityTypeBindingDocumentation
INresponse1..1QuestionnaireResponse

The questionnaire response to be accepted/processed

OUTwarnings0..1OperationOutcome

If the response is successfully procssed, an OperationOutcome may still be returned indicating warnings. For example, identifying questions that were incomplete, answers that were defaulted, etc. It may also convey 'information' messages about the processing of the questionnaire response.

Some receivers may accept responses that are still 'in progress', but others may reject instances with a status other than 'final' or possibly 'amended'. If the operation is invoked on a particular Questionnaire, the submitted QuestionnaireResponse must be a response to the specified Questionnaire. Otherwise, the QuestionnaireResponse will be validated against whatever Questionnaire the QuestionnaireResponse references. It is an error for a QuestionnaireResponse that does not declare a questionnaire to be invoked directly on the Questionnaire endpoint.


Source

{
  "resourceType" : "OperationDefinition",
  "id" : "Questionnaire-process-response",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>SDCQuestionnaireProcessResponse</h2><p>OPERATION: SDCQuestionnaireProcessResponse</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/uv/sdc/OperationDefinition/Questionnaire-process-response</pre><div><p>This operation allows a system to 'receive' a QuestionnaireResponse for a particular Questionnaire. It is intended to be used by systems that expect to receive completed questionnaires but which do not necessarily want to host a RESTful endpoint where those responses are subsequently queryable. The receiver may choose to perform validation of the received response or against local business rules. There no response beyond an HTTP 200 OK if the response is consumed successfully, though an OperationOutcome can optionally be returned identifying warnings. If there are validation or other issues, the operation will fail with details in an OperationOutcome. The specific action that occurs on receipt of a form will depend on both the type of form and the submitter. It could trigger admission to a clinical trial, the beginning of an product investigation, the consideration of a patient's eligibility for coverage, etc. Alternatively, the data may simply be consumed and aggregated with other information for analysis or other use.</p>\n</div><p>URL: [base]/Questionnaire/$process-response</p><p>URL: [base]/Questionnaire/[id]/$process-response</p><p>Input parameters Profile: <a href=\"StructureDefinition-parameters-questionnaire-process-response-in.html\">Questionnaire process response operation input parameters</a></p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>response</td><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4/questionnaireresponse.html\">QuestionnaireResponse</a></td><td/><td><div><p>The questionnaire response to be accepted/processed</p>\n</div></td></tr><tr><td>OUT</td><td>warnings</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/operationoutcome.html\">OperationOutcome</a></td><td/><td><div><p>If the response is successfully procssed, an OperationOutcome may still be returned indicating warnings. For example, identifying questions that were incomplete, answers that were defaulted, etc. It may also convey 'information' messages about the processing of the questionnaire response.</p>\n</div></td></tr></table><div><p>Some receivers may accept responses that are still 'in progress', but others may reject instances with a status other than 'final' or possibly 'amended'. If the operation is invoked on a particular Questionnaire, the submitted QuestionnaireResponse must be a response to the specified Questionnaire. Otherwise, the QuestionnaireResponse will be validated against whatever Questionnaire the QuestionnaireResponse references. It is an error for a QuestionnaireResponse that does not declare a questionnaire to be invoked directly on the Questionnaire endpoint.</p>\n</div></div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger" : 3,
      "_valueInteger" : {
        "extension" : [
          {
            "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical" : "http://hl7.org/fhir/uv/sdc/ImplementationGuide/hl7.fhir.uv.sdc"
          }
        ]
      }
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode" : "trial-use",
      "_valueCode" : {
        "extension" : [
          {
            "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical" : "http://hl7.org/fhir/uv/sdc/ImplementationGuide/hl7.fhir.uv.sdc"
          }
        ]
      }
    }
  ],
  "url" : "http://hl7.org/fhir/uv/sdc/OperationDefinition/Questionnaire-process-response",
  "version" : "3.0.0",
  "name" : "SDCQuestionnaireProcessResponse",
  "title" : "Questionnaire Process Response",
  "status" : "draft",
  "kind" : "operation",
  "date" : "2017-03-19",
  "publisher" : "HL7 International - FHIR Infrastructure Work Group",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description" : "This operation allows a system to 'receive' a QuestionnaireResponse for a particular Questionnaire. It is intended to be used by systems that expect to receive completed questionnaires but which do not necessarily want to host a RESTful endpoint where those responses are subsequently queryable. The receiver may choose to perform validation of the received response or against local business rules. There no response beyond an HTTP 200 OK if the response is consumed successfully, though an OperationOutcome can optionally be returned identifying warnings. If there are validation or other issues, the operation will fail with details in an OperationOutcome. The specific action that occurs on receipt of a form will depend on both the type of form and the submitter. It could trigger admission to a clinical trial, the beginning of an product investigation, the consideration of a patient's eligibility for coverage, etc. Alternatively, the data may simply be consumed and aggregated with other information for analysis or other use.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001"
        }
      ]
    }
  ],
  "code" : "process-response",
  "comment" : "Some receivers may accept responses that are still 'in progress', but others may reject instances with a status other than 'final' or possibly 'amended'. If the operation is invoked on a particular Questionnaire, the submitted QuestionnaireResponse must be a response to the specified Questionnaire. Otherwise, the QuestionnaireResponse will be validated against whatever Questionnaire the QuestionnaireResponse references. It is an error for a QuestionnaireResponse that does not declare a questionnaire to be invoked directly on the Questionnaire endpoint.",
  "resource" : [
    "Questionnaire"
  ],
  "system" : false,
  "type" : true,
  "instance" : true,
  "inputProfile" : "http://hl7.org/fhir/uv/sdc/StructureDefinition/parameters-questionnaire-process-response-in",
  "parameter" : [
    {
      "name" : "response",
      "use" : "in",
      "min" : 1,
      "max" : "1",
      "documentation" : "The questionnaire response to be accepted/processed",
      "type" : "QuestionnaireResponse"
    },
    {
      "name" : "warnings",
      "use" : "out",
      "min" : 0,
      "max" : "1",
      "documentation" : "If the response is successfully procssed, an OperationOutcome may still be returned indicating warnings. For example, identifying questions that were incomplete, answers that were defaulted, etc. It may also convey 'information' messages about the processing of the questionnaire response.",
      "type" : "OperationOutcome"
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.